home *** CD-ROM | disk | FTP | other *** search
- Path: news1.h1.usa.pipeline.com!usenet
- From: grantp@usa.pipeline.com(Pete)
- Newsgroups: comp.os.ms-windows.programmer.tools.mfc,comp.os.ms-windows.apps.compatibility.win95,comp.lang.c++
- Subject: Re: HELP !!! Memory - Allocation
- Date: 28 Jan 1996 15:25:22 GMT
- Organization: Kalevi, Inc.
- Message-ID: <4eg4h2$4he@news1.usa.pipeline.com>
- References: <1996Jan28.015441.7082@mcs.drexel.edu>
- NNTP-Posting-Host: pipe4.h1.usa.pipeline.com
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete)
- X-Newsreader: Pipeline USA v3.3.0
-
- On Jan 28, 1996 01:54:41 in article <Re: HELP !!! Memory - Allocation>,
- 'urcrawfo@mcs.drexel.edu (Programmer)' wrote:
-
- >It is highly recommended using the "new" operator when using C++.
- >It is both practical and effifienct.
- >
- I agree with the recommendation; however, just to set the
- record straight :-)
-
- On some systems, notably g++ 2.6.3, new performs a few
- instructions of its own, then calls malloc. This leads me to
- conclude that new is less efficient than a direct call to
- malloc -- although the margin is probably very narrow.
-
- --
- Pete Grant
- Kalevi, Inc.
- Object Oriented Software Development
-